Data isolation in a blockchain network

ABSTRACT

Implementations of the present specification include receiving a request to perform a private transaction associated with at least one account; in response to receiving the request, performing, by a workflow node, the private transaction; in response to performing the private transaction, generating, by the workflow node, a representation of the private transaction configured to be accessible only to entities that are authorized to access the private transaction; storing, in a private blockchain, the representation of the private transaction; generating, by the workflow node, an account record for the at least one account associated with the private transaction based at least in part on the private transaction, wherein the account record is configured to be accessible to at least one entity that is not authorized to access the representation of the private transaction in the private blockchain; and storing, in a public blockchain, the account record.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/421,170, filed on May 23, 2019, which is a continuation of PCTApplication No. PCT/CN2018/122166, filed on Dec. 19, 2018, and eachapplication is hereby incorporated by reference in its entirety.

BACKGROUND

Distributed ledger systems (DLSs), which can also be referred to asconsensus networks, and/or blockchain networks, enable participatingentities to securely, and immutably store data. DLSs are commonlyreferred to as blockchain networks without referencing any particularuser case (e.g., crypto-currencies). Example types of blockchainnetworks can include public blockchain networks, private blockchainnetworks, and consortium blockchain networks. A public blockchainnetwork is open for all entities to use the DLS, and participate in theconsensus process. A private blockchain network is provided forparticular entity, which centrally controls read and write permissions.A consortium blockchain network is provided for a select group ofentities, which control the consensus process, and includes an accesscontrol layer.

One common issue in blockchain networks is privacy protection, due tothe inherent openness of the blockchain itself. Entries in aconventional blockchain are available for inspection by all participantsin the blockchain network, which can present issues when thetransactions managed in a blockchain network contain sensitiveinformation.

SUMMARY

Implementations of the present specification includecomputer-implemented methods for data isolation in a blockchain network.More particularly, implementations of the present specification aredirected to isolating private transaction details while publishingtransaction summaries to a private blockchain and account balanceupdates to a public blockchain.

In some implementations, actions include receiving a request to performa private transaction associated with at least one account; in responseto receiving the request, performing, by a workflow node, the privatetransaction; in response to performing the private transaction,generating, by the workflow node, a representation of the privatetransaction configured to be accessible only to entities that areauthorized to access the private transaction; storing, in a privateblockchain, the representation of the private transaction; generating,by the workflow node, an account record for the at least one accountassociated with the private transaction based at least in part on theprivate transaction, wherein the account record is configured to beaccessible to at least one entity that is not authorized to access therepresentation of the private transaction in the private blockchain; andstoring, in a public blockchain, the account record.

Other implementations include corresponding systems, apparatus, andcomputer programs, configured to perform the actions of the methods,encoded on computer storage devices.

These and other implementations may each optionally include one or moreof the following features:

In some cases, the workflow node stores the private transaction in adatastore of the workflow node, wherein the datastore is separate fromthe private blockchain, and generating the representation of the privatetransaction includes generating a hash value associated with the privatetransaction.

In some implementations, the workflow node maintains a localrepresentation of the account record for the at least one account,performing the private transaction comprises modifying the localrepresentation of the account record based on the private transaction,and the at least one account record includes a subset of information inthe local representation of the account record.

In some cases, storing the account record in the public blockchain isperformed responsive to storing the representation of the privatetransaction in the private blockchain.

In some implementations, other representations of private transactionsfor which no corresponding storage of an account to the publicblockchain is performed are stored to the private blockchain.

In some cases, an encrypted copy of the private transaction that hasbeen encrypted with a public key of a public/private keypair is storedin a datastore separate from the private blockchain.

In some implementations, storing the encrypted copy of the privatetransaction includes storing a signature of the encrypted copy that hasbeen created with a private key of the public/private keypair.

In some implementations, the private blockchain is a first privateblockchain, the private transaction is a first private transaction, andthe method further comprises: storing, in a second private blockchainseparate from the first private blockchain, a representation of a secondprivate transaction different from the first private transaction; andstoring, in the public blockchain, an account record for an accountassociated with the second private transaction.

In some cases, the account record includes a balance of the at least oneaccount and the account record does not include information about theassociated private transaction.

The present specification also provides one or more non-transitorycomputer-readable storage media coupled to one or more processors andhaving instructions stored thereon which, when executed by the one ormore processors, cause the one or more processors to perform operationsin accordance with implementations of the methods provided herein.

The present specification further provides a system for implementing themethods provided herein. The system includes one or more processors, anda computer-readable storage medium coupled to the one or more processorshaving instructions stored thereon which, when executed by the one ormore processors, cause the one or more processors to perform operationsin accordance with implementations of the methods provided herein.

It is appreciated that methods in accordance with the presentspecification may include any combination of the aspects and featuresdescribed herein. That is, methods in accordance with the presentspecification are not limited to the combinations of aspects andfeatures specifically described herein, but also include any combinationof the aspects and features provided.

The details of one or more implementations of the present specificationare set forth in the accompanying drawings and the description below.Other features and advantages of the present specification will beapparent from the description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 depicts an example of an environment that can be used to executeimplementations of the present specification.

FIG. 2 depicts an example of an architecture in accordance withimplementations of the present specification.

FIG. 3 depicts an example of a system for providing data isolation in ablockchain network in accordance with implementations of the presentspecification.

FIG. 4 depicts an example of a process for providing data isolation in ablockchain network in accordance with implementations of the presentspecification.

FIG. 5 depicts an example of a process that can be executed inaccordance with implementations of the present specification.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

Implementations of the present specification includecomputer-implemented methods for data isolation in a blockchain network.More particularly, implementations of the present specification aredirected to isolating private transaction details while publishingtransaction summaries to a private blockchain and account balanceupdates to a public blockchain. In some implementations, actions includereceiving a request to perform a private transaction associated with atleast one account; in response to receiving the request, performing, bya workflow node, the private transaction; in response to performing theprivate transaction, generating, by the workflow node, a representationof the private transaction configured to be accessible only to entitiesthat are authorized to access the private transaction; storing, in aprivate blockchain, the representation of the private transaction;generating, by the workflow node, an account record for the at least oneaccount associated with the private transaction based at least in parton the private transaction, wherein the account record is configured tobe accessible to at least one entity that is not authorized to accessthe representation of the private transaction in the private blockchain;and storing, in a public blockchain, the account record.

To provide further context for implementations of the presentspecification, and as introduced above, distributed ledger systems(DLSs), which can also be referred to as consensus networks (e.g., madeup of peer-to-peer nodes), and blockchain networks, enable participatingentities to securely, and immutably conduct transactions, and storedata. Although the term blockchain is generally associated withcrypto-currency networks, blockchain is used herein to generally referto a DLS without reference to any particular use case.

A blockchain is a data structure that stores transactions in a way thatthe transactions are immutable, and can be subsequently verified. Ablockchain includes one or more blocks. Each block in the chain islinked to a previous block immediately before it in the chain byincluding a cryptographic hash of the previous block. Each block alsoincludes a timestamp, its own cryptographic hash, and one or moretransactions. The transactions, which have already been verified by thenodes of the blockchain network, are hashed and encoded into a Merkletree. A Merkle tree is a data structure in which data at the leaf nodesof the tree is hashed, and all hashes in each branch of the tree areconcatenated at the root of the branch. This process continues up thetree to the root of the entire tree, which stores a hash that isrepresentative of all data in the tree. A hash purporting to be of atransaction stored in the tree can be quickly verified by determiningwhether it is consistent with the structure of the tree.

Whereas a blockchain is a data structure for storing transactions, ablockchain network is a network of computing nodes that manage, update,and maintain one or more blockchains. As introduced above, a blockchainnetwork can be provided as a public blockchain network, a privateblockchain network, or a consortium blockchain network.

In a public blockchain network, the consensus process is controlled bynodes of the consensus network. For example, hundreds, thousands, evenmillions of entities can cooperate a public blockchain network, each ofwhich operates at least one node in the public blockchain network.Accordingly, the public blockchain network can be considered a publicnetwork with respect to the participating entities. In some examples, amajority of entities (nodes) must sign every block in order for theblock to be valid, and added to the blockchain (distributed ledger) ofthe blockchain network. Examples of public blockchain networks includecrypto-currency networks, which are a peer-to-peer payment network. Asnoted above, the term blockchain, however, is used to generally refer todistributed ledgers without particular reference to any particularblockchain network

In general, a public blockchain network supports public transactions. Apublic transaction is shared with all of the nodes within the publicblockchain network, and are stored in a global blockchain. A globalblockchain is a blockchain that is replicated across all nodes. That is,all nodes are in perfect state consensus with respect to the globalblockchain. To achieve consensus (e.g., agreement to the addition of ablock to a blockchain), a consensus protocol is implemented within thepublic blockchain network. Examples of consensus protocols include,without limitation, proof-of-work (POW) (e.g., implemented in the somecrypto-currency networks), proof-of-stake (POS), and proof-of-authority(POA). POW is referenced further herein as a non-limiting example.

In general, a private blockchain network private blockchain network isprovided for a particular entity, which centrally controls read andwrite permissions. The entity controls, which nodes are able toparticipate in the blockchain network. Consequently, private blockchainnetworks are generally referred to as permissioned networks that placerestrictions on who is allowed to participate in the network, and ontheir level of participation (e.g., only in certain transactions).Various types of access control mechanisms can be used (e.g., existingparticipants vote on adding new entities, a regulatory authority cancontrol admission).

In general, a consortium blockchain network is private among theparticipating entities. In a consortium blockchain network, theconsensus process is controlled by an authorized set of nodes, one ormore nodes being operated by a respective entity (e.g., a financialinstitution, insurance company). For example, a consortium of ten (10)entities (e.g., financial institutions, insurance companies) can operatea consortium blockchain network, each of which operates at least onenode in the consortium blockchain network. Accordingly, the consortiumblockchain network can be considered a private network with respect tothe participating entities. In some examples, each entity (node) mustsign every block in order for the block to be valid, and added to theblockchain. In some examples, at least a sub-set of entities (nodes)(e.g., at least 7 entities) must sign every block in order for the blockto be valid, and added to the blockchain.

Implementations of the present specification are described in furtherdetail herein with reference to a public blockchain network, which ispublic among the participating entities. It is contemplated, however,that implementations of the present specification can be realized in anyappropriate type of blockchain network.

Implementations of the present specification are described in furtherdetail herein in view of the above context. More particularly, and asintroduced above, implementations of the present specification aredirected to isolation of sensitive transaction data in a blockchainnetwork.

In a conventional blockchain network, transactions that are recorded inthe blockchain are publicly available. However, in many financialscenarios, the details of such transactions include sensitiveinformation that the transaction participants do not wish to makepublic. For example, a participant in the blockchain network may want tohide its transactions from a competing entity also participating in theblockchain network.

The techniques described herein provide a technical solution to thetechnical problem of data isolation in a blockchain network. Forexample, transaction detail data can be locally stored by workflow nodesin the blockchain network, and verified through out-of-chaincollaboration. Selected information from the transaction detail data(e.g., the participants in the transaction) can be stored in a privateblockchain accessible only to the workflow nodes. Account statuses(e.g., balances) for the participants can be stored in a publicblockchain for inspection and verification by all network participants,and can be updated as new transactions are processed.

FIG. 1 depicts an example of an environment 100 that can be used toexecute implementations of the present specification. In some examples,the example environment 100 enables entities to participate in ablockchain network 102. The example environment 100 includes computingdevices 106, 108, and a network 110. In some examples, the network 110includes a local area network (LAN), wide area network (WAN), theInternet, or a combination thereof, and connects web sites, user devices(e.g., computing devices), and back-end systems. In some examples, thenetwork 110 can be accessed over a wired and/or a wirelesscommunications link. In general the network 110 represents one or morecommunication networks. In some cases, the computing devices 106, 108can be nodes of a cloud computing system (not shown), or can eachcomputing device 106, 108 be a separate cloud computing system includinga plurality of computers interconnected by a network and functioning asa distributed processing system.

In the depicted example, the computing systems 106, 108 can each includeany appropriate computing system that enables participation as a node inthe blockchain network 102. Example computing devices include, withoutlimitation, a server, a desktop computer, a laptop computer, a tabletcomputing device, and a smartphone. In some examples, the computingsystems 106, 108 hosts one or more computer-implemented services forinteracting with the blockchain network 102. For example, the computingsystem 106 can host computer-implemented services of a first entity(e.g., user A), such as transaction management system that the firstentity uses to manage its transactions with one or more other entities(e.g., other users). The computing system 108 can hostcomputer-implemented services of a second entity (e.g., user B), such astransaction management system that the second entity uses to manage itstransactions with one or more other entities (e.g., other users). In theexample of FIG. 1, the blockchain network 102 is represented as apeer-to-peer network of nodes, and the computing systems 106, 108provide nodes of the first entity, and second entity respectively, whichparticipate in the blockchain network 102.

FIG. 2 depicts an example of an architecture 200 in accordance withimplementations of the present specification. The example conceptualarchitecture 200 includes an entity layer 202, a hosted services layer204, and a blockchain network layer 206. In the depicted example, theentity layer 202 includes three entities, Entity_1 (E1), Entity_2 (E2),and Entity_3 (E3), each entity having a respective transactionmanagement system 208.

In the depicted example, the hosted services layer 204 includesinterfaces 210 for each transaction management system 210. In someexamples, a respective transaction management system 208 communicateswith a respective interface 210 over a network (e.g., the network 110 ofFIG. 1) using a protocol (e.g., hypertext transfer protocol secure(HTTPS)). In some examples, each interface 210 provides communicationconnection between a respective transaction management system 208, andthe blockchain network layer 206. More particularly, the interface 210communicate with a blockchain network 212 of the blockchain networklayer 206. In some examples, communication between an interface 210, andthe blockchain network layer 206 is conducted using remote procedurecalls (RPCs). In some examples, the interfaces 210 “host” blockchainnetwork nodes for the respective transaction management systems 208. Forexample, the interfaces 210 provide the application programminginterface (API) for access to blockchain network 212.

As described herein, the blockchain network 212 is provided as apeer-to-peer network including a plurality of nodes 214 that immutablyrecord information in a blockchain 216. Although a single blockchain 216is schematically depicted, multiple copies of the blockchain 216 areprovided, and are maintained across the blockchain network 212. Forexample, each node 214 stores a copy of the blockchain. In someimplementations, the blockchain 216 stores information associated withtransactions that are performed between two or more entitiesparticipating in the blockchain network.

FIG. 3 depicts an example of a system 300 for providing data isolationin a blockchain network in accordance with implementations of thepresent specification. As shown, the system 300 includes a publicblockchain network 305 including blockchain nodes 310A-D maintaining apublic blockchain 330. System 300 further includes a private blockchainnetwork 310 including workflow nodes 320A-D. Each workflow node 320A-Dis associated with a local storage device 325A-D. The workflow nodes320A-D maintain a private blockchain 340 separate from the publicblockchain 330. In some implementations, the workflow nodes 320A-D mayalso function as blockchain nodes of the public blockchain network 305by participating in the creation and verification of new blocks to beadded to the public blockchain 330.

In operation, the workflow nodes 320A-D receive private transactions tobe performed and stored in the system 300. In some cases, a client ofthe system 300 may submit a transaction to one of the blockchain nodes310A-D or the workflow nodes 320A-D. In some cases, the transaction maybe between two or more entities that operate one or more of theblockchain nodes 310A-D or the workflow nodes 320A-D, in which case thetransaction may be received from one or more of these participantentities at a controlled workflow node. In some implementations, theblockchain nodes 310A-D may be configured to forward new transactions tothe workflow nodes 320A-D for processing rather than recording them inthe public blockchain 330.

In some implementations, each workflow node 320A-D stores receivedtransaction data in its local storage 325A-D. In some implementations,the local storage 325A-D may be storage devices coupled to theassociated workflow node 320A-D, such as, for example, hard drives,random access memory (RAM), flash memory, or other storage devices. Insome cases, local storage 325A-D may store shards of a distributeddatabase maintained by the workflow nodes 320A-D.

In some implementations, when a workflow node (e.g., 320A) receives anew transaction, the workflow node 320A verifies the transaction(described in greater detail below), and performs any actions associatedwith the transaction that it is responsible for (e.g., debiting andcredit accounts at the participant financial institutions, executingsmart contract instructions, etc.). In some cases, the workflow node320A generates a representation of the private transaction for storagein the private blockchain 340. For example, the workflow node 320A maygenerate a representation of the transaction including a hash of thetransaction data, and the identities of all transaction participants. Insome implementations, each private transaction will be cryptographicallysigned by all transaction participants. The workflow node 320A caninclude these digital signatures in the representation of the privatetransaction stored in the private blockchain 340. The workflow 320A mayalso store the raw private transaction data in its local storage 325A.By organizing the transaction data in this manner, sensitive transactiondata (e.g., the amounts associated with the transaction) can be storedlocally by the workflow nodes 320A-D and thus kept secret, while theprivate blockchain 340 can serve as the consensus record of all privatetransactions in the system. In some implementations, the privatetransaction data is stored in the local storage 325A-D of workflow nodes320A-D that are controlled by the entities participating in thetransaction, thus isolating the private transaction data from otherentities. In some cases, the workflow nodes 320A-D maintain the privateblockchain 340 according to conventional consensus methods.

In some implementations, the workflow node 320A, after performing theabove-described actions on the private blockchain network 310, theworkflow node 320 a generates account records for the participants inthe private transaction for inclusion in the public blockchain 330. Theaccount records include updated balances for the accounts of theparticipants in the private transaction after the private transactionhas been performed. For example, if workflow node 320A received aprivate transaction where account A transferred $10 to account B,workflow node 320A could generate an account record debiting account A'sbalance by $10, and another account record crediting account B's balanceby $10. The generated account records can be sent to the publicblockchain network 305 for inclusion in the public blockchain 330, suchas by the workflow node 320A broadcasting the account records to theblockchain nodes 310A-D.

In some implementations, the workflow node 320A may be configured towait until a certain number of transactions have been performedinvolving a particular entity before updating the entity's accountbalance on the public blockchain 330. For example, the workflow node320A may publish a new account record and balance for account A onlyafter processing three transactions involving account A. Delaying theaccount balance updates may prevent an observer from deducingtransaction details based on the changes in the account balances. Forexample, if the system were to update the account balance after eachtransaction, an observer could deduce that account A paid account B $10by noting that account A's balance was debited by $10 and account B'sbalance was credited by the same amount. By making each account balanceupdate reflect changes made by multiple transactions, the individualtransaction details become more difficult to deduce.

FIG. 4 depicts an example of a process 400 for providing data isolationin a blockchain network in accordance with implementations of thepresent specification. As shown, the process involves workflow nodes320A and 320B, and blockchain node 310A from FIG. 3. At 415, workflownode 320A proposes a private transaction to workflow node 320B. Forexample, the private transaction may be a transaction between the entitycontrolling workflow node 320A and the entity controlling workflow node320B. In some cases, workflow node 320A cryptographically signs theproposed transaction so the workflow node 320B can verify that identityof the entity proposing the transaction.

At 420, the workflow node 320B verifies the proposed transaction usingits private state and/or the private blockchain 340. For example, theworkflow node 320B may verify that the account associated with theworkflow node 320A has sufficient funds to cover the transaction; thatthe account is the owner of assets (e.g., currency) to be transferred;or other information about the private transaction.

At 425, the workflow node 320B notifies the workflow node 320A that thetransaction has been successfully verified, and returns its digitalsignature to prove its identity. At 430 and 435, the workflow nodes320A, B update their respective private states (e.g., local storage325A, B) to include the agreed-upon private transaction. At 440, theworkflow node 320A stores a representation of the private transaction inthe private blockchain 340, as described above.

At 445, the workflow node 320A updates the status of the accounts (bygenerating account records, as described above) associated with workflownodes 320A and 320B by sending a notification to blockchain node 310A,which will store the updates in the public blockchain 330. As previouslydiscussed, the workflow node 320A may be configured to provide accountbalance updates after a certain number of private transactions have beenprocessed for the transaction participants in order to prevent observersfrom deducing the transaction details from the account balance updates.

FIG. 5 depicts an example of a process 500 that can be executed inaccordance with implementations of the present specification. In someimplementations, the example process 500 may be performed using one ormore computer-executable programs executed using one or more computingdevices.

At 505, a request to perform a private transaction associated with atleast one account is received by a workflow node.

At 510, in response to receiving the request, the workflow node performsthe requested private transaction.

At 515, in response to performing the private transaction, the workflownode generates a representation of the private transaction configured tobe accessible only to entities that are authorized to access the privatetransaction.

At 520, the representation of the private transaction is stored in aprivate blockchain. In some cases, the workflow node stores the privatetransaction in a datastore of the workflow node, wherein the datastoreis separate from the private blockchain, and generating therepresentation of the private transaction includes generating a hashvalue associated with the private transaction.

At 525, the workflow node generates an account record for the at leastone account associated with the private transaction based at least inpart on the private transaction, wherein the account record isconfigured to be accessible to at least one entity that is notauthorized to access the representation of the private transaction inthe private blockchain. In some implementations, the workflow nodemaintains a local representation of the account record for the at leastone account, performing the private transaction comprises modifying thelocal representation of the account record based on the privatetransaction, and the at least one account record includes a subset ofinformation in the local representation of the account record. In somecases, the account record includes a balance of the at least one accountand the account record does not include information about the associatedprivate transaction.

At 530, the account record is stored in a public blockchain. In somecases, storing the account records to the public blockchain is performedresponsive to storing the representation of the private transaction tothe private blockchain.

In some implementations, other representations of private transactionsfor which no corresponding storage of an account to the publicblockchain is performed are stored in the private blockchain.

In some cases, an encrypted copy of the private transaction that hasbeen encrypted with a public key of a public/private keypair is storedin a datastore separate from the private blockchain,

In some implementations, the private blockchain is a first privateblockchain, the private transaction is a first private transaction, andthe method further comprises: storing, in a second private blockchainseparate from the first private blockchain, a representation of a secondprivate transaction different from the first private transaction; andstoring, in the public blockchain, an account record for an accountassociated with the second private transaction.

Implementations of the subject matter and the actions and operationsdescribed in this specification can be implemented in digital electroniccircuitry, in tangibly-embodied computer software or firmware, incomputer hardware, including the structures disclosed in thisspecification and their structural equivalents, or in combinations ofone or more of them. Implementations of the subject matter described inthis specification can be implemented as one or more computer programs,e.g., one or more modules of computer program instructions, encoded on acomputer program carrier, for execution by, or to control the operationof, data processing apparatus. The carrier may be a tangiblenon-transitory computer storage medium. Alternatively, or in addition,the carrier may be an artificially-generated propagated signal, e.g., amachine-generated electrical, optical, or electromagnetic signal that isgenerated to encode information for transmission to suitable receiverapparatus for execution by a data processing apparatus. The computerstorage medium can be or be part of a machine-readable storage device, amachine-readable storage substrate, a random or serial access memorydevice, or a combination of one or more of them. A computer storagemedium is not a propagated signal.

The term “data processing apparatus” encompasses all kinds of apparatus,devices, and machines for processing data, including by way of example aprogrammable processor, a computer, or multiple processors or computers.Data processing apparatus can include special-purpose logic circuitry,e.g., an FPGA (field programmable gate array), an ASIC(application-specific integrated circuit), or a GPU (graphics processingunit). The apparatus can also include, in addition to hardware, codethat creates an execution environment for computer programs, e.g., codethat constitutes processor firmware, a protocol stack, a databasemanagement system, an operating system, or a combination of one or moreof them.

A computer program, which may also be referred to or described as aprogram, software, a software application, an app, a module, a softwaremodule, an engine, a script, or code, can be written in any form ofprogramming language, including compiled or interpreted languages, ordeclarative or procedural languages; and it can be deployed in any form,including as a stand-alone program or as a module, component, engine,subroutine, or other unit suitable for executing in a computingenvironment, which environment may include one or more computersinterconnected by a data communication network in one or more locations.

A computer program may, but need not, correspond to a file in a filesystem. A computer program can be stored in a portion of a file thatholds other programs or data, e.g., one or more scripts stored in amarkup language document, in a single file dedicated to the program inquestion, or in multiple coordinated files, e.g., files that store oneor more modules, sub-programs, or portions of code.

The processes and logic flows described in this specification can beperformed by one or more computers executing one or more computerprograms to perform operations by operating on input data and generatingoutput. The processes and logic flows can also be performed byspecial-purpose logic circuitry, e.g., an FPGA, an ASIC, or a GPU, or bya combination of special-purpose logic circuitry and one or moreprogrammed computers.

Computers suitable for the execution of a computer program can be basedon general or special-purpose microprocessors or both, or any other kindof central processing unit. Generally, a central processing unit willreceive instructions and data from a read-only memory or a random accessmemory or both. Elements of a computer can include a central processingunit for executing instructions and one or more memory devices forstoring instructions and data. The central processing unit and thememory can be supplemented by, or incorporated in, special-purpose logiccircuitry.

Generally, a computer will be coupled to at least one non-transitorycomputer-readable storage medium (also referred to as acomputer-readable memory). The storage medium coupled to the computercan be an internal component of the computer (e.g., an integrated harddrive) or an external component (e.g., universal serial bus (USB) harddrive or a storage system accessed over a network). Examples of storagemedia can include, for example, magnetic, magneto-optical, or opticaldisks, solid state drives, network storage resources such as cloudstorage systems, or other types of storage media. However, a computerneed not have such devices. Moreover, a computer can be embedded inanother device, e.g., a mobile telephone, a personal digital assistant(PDA), a mobile audio or video player, a game console, a GlobalPositioning System (GPS) receiver, or a portable storage device, e.g., auniversal serial bus (USB) flash drive, to name just a few.

To provide for interaction with a user, implementations of the subjectmatter described in this specification can be implemented on, orconfigured to communicate with, a computer having a display device,e.g., a LCD (liquid crystal display) monitor, for displaying informationto the user, and an input device by which the user can provide input tothe computer, e.g., a keyboard and a pointing device, e.g., a mouse, atrackball or touchpad. Other kinds of devices can be used to provide forinteraction with a user as well; for example, feedback provided to theuser can be any form of sensory feedback, e.g., visual feedback,auditory feedback, or tactile feedback; and input from the user can bereceived in any form, including acoustic, speech, or tactile input. Inaddition, a computer can interact with a user by sending documents toand receiving documents from a device that is used by the user; forexample, by sending web pages to a web browser on a user's device inresponse to requests received from the web browser, or by interactingwith an app running on a user device, e.g., a smartphone or electronictablet. Also, a computer can interact with a user by sending textmessages or other forms of message to a personal device, e.g., asmartphone that is running a messaging application, and receivingresponsive messages from the user in return.

This specification uses the term “configured to” in connection withsystems, apparatus, and computer program components. For a system of oneor more computers to be configured to perform particular operations oractions means that the system has installed on it software, firmware,hardware, or a combination of them that in operation cause the system toperform the operations or actions. For one or more computer programs tobe configured to perform particular operations or actions means that theone or more programs include instructions that, when executed by dataprocessing apparatus, cause the apparatus to perform the operations oractions. For special-purpose logic circuitry to be configured to performparticular operations or actions means that the circuitry has electroniclogic that performs the operations or actions.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of what isbeing claimed, which is defined by the claims themselves, but rather asdescriptions of features that may be specific to particularimplementations. Certain features that are described in thisspecification in the context of separate implementations can also berealized in combination in a single implementation. Conversely, variousfeatures that are described in the context of a single implementationscan also be realized in multiple implementations separately or in anysuitable subcombination. Moreover, although features may be describedabove as acting in certain combinations and even initially be claimed assuch, one or more features from a claimed combination can in some casesbe excised from the combination, and the claim may be directed to asubcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings and recited inthe claims in a particular order, this should not be understood asrequiring that such operations be performed in the particular ordershown or in sequential order, or that all illustrated operations beperformed, to achieve desirable results. In certain circumstances,multitasking and parallel processing may be advantageous. Moreover, theseparation of various system modules and components in theimplementations described above should not be understood as requiringsuch separation in all implementations, and it should be understood thatthe described program components and systems can generally be integratedtogether in a single software product or packaged into multiple softwareproducts.

Particular implementations of the subject matter have been described.Other implementations are within the scope of the following claims. Forexample, the actions recited in the claims can be performed in adifferent order and still achieve desirable results. As one example, theprocesses depicted in the accompanying figures do not necessarilyrequire the particular order shown, or sequential order, to achievedesirable results. In some cases, multitasking and parallel processingmay be advantageous.

What is claimed is:
 1. A computer-implemented method, comprising:repeatedly performing the following operations to process one or moretransactions: performing, by a node belonging to a first distributedledger network, a transaction that is submitted by a user of the firstdistributed ledger network and that is associated with two or morerespective transaction participants; and generating, by the nodebelonging to the first distributed ledger network, a privaterepresentation of the transaction that is accessible only to the two ormore respective transaction participants for storage in the firstdistributed ledger network, the private representation of thetransaction comprising a hash of the transaction; determining whether acondition for releasing information that relates to the one or moretransactions has been satisfied; in response to a positivedetermination, releasing information that relates to the one or moretransactions including: generating, by the node belonging to the firstdistributed ledger network and based on the one or more transactionsthat have been performed, a public representation accessible to at leastone node belonging to a second distributed ledger network, the publicrepresentation specifying an account balance update of each of the twoor more respective transaction participants as a result of the one ormore transactions; and broadcasting, by the node belonging to the firstdistributed ledger network, the public representation for inclusion inthe second distributed ledger network.
 2. The computer-implementedmethod of claim 1, wherein: the first distributed ledger network ismanaged by a financial institution; and the second distributed ledgernetwork is a public blockchain network.
 3. The computer-implementedmethod of claim 1, further comprising: storing, by the node belonging tothe first distributed ledger network, the transaction in a datastore ofthe node, wherein the datastore is separate from the first distributedledger network.
 4. The computer-implemented method of claim 1, whereingenerating the private representation of the transaction furthercomprises generating representation of respective identities of the twoor more transaction participants.
 5. The computer-implemented method ofclaim 1, wherein generating the public representation of the transactioncomprises generating respective account records of the two or moretransaction participants.
 6. The computer-implemented method of claim 1,the method further comprising: maintaining, by the node belonging to thefirst distributed ledger network, a local representation of respectiveaccount records of the two or more transaction participants; whereinperforming the transaction comprises modifying the local representationof the respective account records based on the transaction; and whereineach of the respective account records includes a subset of informationin the local representation of the respective account records.
 7. Thecomputer-implemented method of claim 1, wherein broadcasting the publicrepresentation of the transaction for inclusion in the seconddistributed ledger network is performed after storing the privaterepresentation of the transaction in the first distributed ledgernetwork.
 8. The computer-implemented method of claim 1, furthercomprising: storing, in a datastore separate from the first distributedledger network, an encrypted copy of the transaction that has beenencrypted with a public key of a public/private keypair.
 9. Thecomputer-implemented method of claim 8, wherein storing the encryptedcopy of the transaction includes storing a signature of the encryptedcopy that has been created with a private key of the public/privatekeypair.
 10. The computer-implemented method of claim 1, furthercomprising: storing, in a third distributed ledger network that isdifferent from the first distributed ledger network, a privaterepresentation of another transaction that is different from the privaterepresentation generated by the node belonging to the first distributedledger network; comparing, by a node belonging to the first distributedledger network, a quantity of transactions performed to a thresholdrepresenting a predetermined quantity of transactions; determining, by anode belonging to the first distributed ledger network and based on theresult of comparing the quantity of transactions to the threshold, thatan account record for a transaction participant associated with theother transaction can be stored in the second distributed ledgernetwork; and storing, in the second distributed ledger network, theaccount record for the transaction participant associated with the othertransaction.
 11. A non-transitory computer-readable storage mediumstoring one or more instructions executable by a computer system toperform operations comprising: repeatedly performing the followingoperations to process one or more transactions, performing, by a nodebelonging to a first distributed ledger network, a transaction that issubmitted by a user of the first distributed ledger network and that isassociated with two or more respective transaction participants; andgenerating, by the node belonging to the first distributed ledgernetwork, a private representation of the transaction that is accessibleonly to the two or more respective transaction participants for storagein the first distributed ledger network, the private representation ofthe transaction comprising a hash of the transaction; determiningwhether a condition for releasing information that relates to the one ormore transactions has been satisfied; in response to a positivedetermination, releasing information that relates to the one or moretransactions including: generating, by the node belonging to the firstdistributed ledger network and based on the one or more transactionsthat have been performed, a public representation accessible to at leastone node belonging to a second distributed ledger network, the publicrepresentation specifying an account balance update of each of the twoor more respective transaction participants as a result of the one ormore transactions; and broadcasting, by the node belonging to the firstdistributed ledger network, the public representation for inclusion inthe second distributed ledger network.
 12. The non-transitorycomputer-readable medium of claim 11, wherein: the first distributedledger network is managed by a financial institution; and the seconddistributed ledger network is a public blockchain network.
 13. Thenon-transitory computer-readable medium of claim 11, wherein theoperations further comprise: storing, by the node belonging to the firstdistributed ledger network, the transaction in a datastore of the node,wherein the datastore is separate from the first distributed ledgernetwork.
 14. The non-transitory computer-readable medium of claim 11,wherein generating the private representation of the transaction furthercomprises generating representation of respective identities of the twoor more transaction participants.
 15. The non-transitorycomputer-readable medium of claim 11, wherein generating the publicrepresentation of the transaction comprises generating respectiveaccount records of the two or more transaction participants.
 16. Thenon-transitory computer-readable medium of claim 11, wherein theoperations further comprise: maintaining, by the node belonging to thefirst distributed ledger network, a local representation of respectiveaccount records of the two or more transaction participants; whereinperforming the transaction comprises modifying the local representationof the respective account records based on the transaction; and whereineach of the respective account records includes a subset of informationin the local representation of the respective account records.
 17. Thenon-transitory computer-readable medium of claim 11, whereinbroadcasting the public representation of the transaction for inclusionin the second distributed ledger network is performed after storing theprivate representation of the transaction in the first distributedledger network.
 18. The non-transitory computer-readable medium of claim11, wherein the operations further comprise: storing, in a datastoreseparate from the first distributed ledger network, an encrypted copy ofthe transaction that has been encrypted with a public key of apublic/private keypair.
 19. The non-transitory computer-readable mediumof claim 18, wherein storing the encrypted copy of the transactionincludes storing a signature of the encrypted copy that has been createdwith a private key of the public/private keypair.
 20. A system,comprising: one or more computers; and one or more computer memorydevices interoperably coupled with the one or more computers and havingtangible, non-transitory, machine-readable media storing one or moreinstructions that, when executed by the one or more computers, performone or more operations comprising: repeatedly performing the followingoperations to process one or more transactions; performing, by a nodebelonging to a first distributed ledger network, a transaction that issubmitted by a user of the first distributed ledger network and that isassociated with two or more respective transaction participants; andgenerating, by the node belonging to the first distributed ledgernetwork, a private representation of the transaction that is accessibleonly to the two or more respective transaction participants for storagein the first distributed ledger network, the private representation ofthe transaction comprising a hash of the transaction; determiningwhether a condition for releasing information that relates to the one ormore transactions has been satisfied; in response to a positivedetermination, releasing information that relates to the one or moretransactions including: generating, by the node belonging to the firstdistributed ledger network and based on the one ore more transactionsthat have been performed, a public representation accessible to at leastone node belonging to a second distributed ledger network, the publicrepresentation specifying an account balance update of each of the twoor more respective transaction participants as a result of the one ormore transactions; and broadcasting, by the node belonging to the firstdistributed ledger network, the public representation for inclusion inthe second distributed ledger network.
 21. The method of claim 1,wherein determining whether the condition for releasing information thatrelates to the one or more transactions has been satisfied comprises:determining that a predetermined number of transactions have beenperformed at the first distributed ledger network.